@Hirokazu-Tei So you have two Omegas, one of them Omega2 with a fairly old v0.1.5-b130 FW and its Internet connection works sometimes. These are the latest FWs in http://repo.onion.io/omega2/images/ with the MediaTek WiFi driver v0.1.10-b160 with the new Warp Core WiFi driver v0.2.0-b192 Try to download one of them directly to your Omega2 and install it - for example: cd /tmp wget http://repo.onion.io.s3.amazonaws.com/omega2/images/omega2-v0.2.0-b192.bin (or try to copy the downloaded file from your desktop to the /tmp dir of your Omega2) sysupgrade omega2-v0.2.0-b192.bin BTW What type of dock and extension do you have please? Good luck!

@Christian-Toller in the omega2 /etc/config/wireless you are missing the > in '<router SSID' for both instances. not that it matters, i just noticed when reading. it's a good guide should i have the problem. it was either you or someone else that mentioned this issue before and as i result i tested my omega2 devices by unplugging my router they connect to and all 3 of them had no issue with reconnecting once the router was back up so i started to think it might be an issue with your specific router but did not know of the re-write of the file at the time so i'll have to go and check the files before & after the next time i test.

Also my check script with wifi restart that WORKS ! #next line is to test if previous instance of test.sh is still running - in case u run connectivity test every few seconds test1=$(ps |grep "test.sh" |grep -v grep |wc -l) PINGTEST=$(ping www.google.com -c1 -W3|grep loss| awk {'print $7'}) if [[ "$PINGTEST" != "0%" ]] && [[ $test1 == "0" ]] ; then /bin/sh test.sh fi #also what i do after negative test result on connectivity (test.sh): #! /bin/sh /sbin/uci set wireless.ra0.disabled=1 /sbin/uci commit wireless /sbin/reload_config /bin/sleep 30 /sbin/uci set wireless.ra0.disabled=0 /sbin/uci commit wireless /sbin/reload_config /bin/sleep 30 /usr/bin/wifimanager -v Like i said in case somebody needs the script to REALLY restart the whole wifi procedure. Please change the line: PINGTEST=$(ping www.google.com -c1 -W3|grep loss| awk {'print $7'}) replace www.google.com with some other address as I don't think google guys will appreciate all the pings to their server Lets say some server u rely on but under your control - again not to "attack" somebody BR Ales

Root cause is: netifd does support iface events UP and DOWN but does not support something like "up failure" (I mean, there is no event fired after iface connection failed, only for UP and DOWN). Afaik.

Look at: https://community.onion.io/topic/2446/omega2-cannot-reconnect-to-wifi-automatically

@magouero said in wifi disconnect: @György-Farkas Köszönöm. Szívesen. The only difference is: "config interface 'wan' option ifname 'eth0.2' => here you have eth0 option proto 'dhcp' " Do you know what this " .2 " means ? I don't know too much. eth0 is a physical network interface (a hardware device), eth0.1, eth0.2, ... are virtual network interfaces (not an existent hardware device but are linked to one). root@Omega-5BE1:~# ifconfig apcli0 Link encap:Ethernet HWaddr 42:A3:6B:00:5B:E1 ... br-wlan Link encap:Ethernet HWaddr 40:A3:6B:C0:5B:E3 ... eth0 Link encap:Ethernet HWaddr 40:A3:6B:C0:5B:E3 Interrupt:5 ... eth0.1 Link encap:Ethernet HWaddr 40:A3:6B:C0:5B:E3 ... lo Link encap:Local Loopback ... ra0 Link encap:Ethernet HWaddr 40:A3:6B:C0:5B:E1 Interrupt:6 Do you have an Ethernet Expansion? Did you modify any network / firewall config files? It seems the DHCP client is working well on my almost "default" Omega2+ (Wifi AP 192.168.3.1, client 192.168.100.x connected to my Internet gateway).